[libressl] add download mirror#11949
Conversation
NancyLi1013
left a comment
There was a problem hiding this comment.
Could you please also bump the version as 2.9.1-3 in ports/libressl/CONTROL file?
Update the deprecated functions or variables
|
Hi @Maximus5 It failed on x64-windows due to this: Could you please try to fix this? |
|
It works with tools now |
|
It can be built with PS F:\11949\vcpkg> .\vcpkg.exe install libressl[tools]:x64-windows Total elapsed time: 7.991 min |
|
That |
|
@NancyLi1013 Well, I've made investigations and this stuff is because of the bug in vcpkg/stl.
From my point of view, there is two problems here and both are out of scope of this PR
|
|
Hi @Maximus5 |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Hi |
|
Hi @Maximus5 On master, it seems there is no this error. |
|
Strange. I had no such errors locally (Windows 10). |
|
Commenter does not have sufficient privileges for PR 11949 in repo microsoft/vcpkg |
|
Could you recheck this please? |
|
It might be something with my local environment. I will check this again. Let's waiting for CI checks. Once all passed, it can be merged. Edit: I test this on my another machine, but there is still the same error. |
Doesn't that mean something wrong is with CI? |
|
Yes, there is something wrong with our CI. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@strega-nil |
|
@NancyLi1013 Are you sure you are using fresh vcpkg.exe? For me similar error appears only if I build vcpkg from 830893f and before (without this PR changes definitely). What OS and compiler is that? You have Also I have only VS 2019 installed on my PC. |
|
Hi @Maximus5 I clone a new repro to build this and there is still the same error. I can confirm I have got the latest commit. I try to build this on two machines and they failed with the same error. One is Visual Studio 2017, another is Vistudio 2019. Both are on Windows 10. I don't know what caused this error info. |
|
This is really unfortunate; it looks like libressl requires permissions to create symbolic links (cc @BillyONeal for an example of a port that does this). I'm not sure how to solve this; it means that we can't currently deal with libressl on Windows. However, it is an existing error. I'd recommend marking it Also, fwiw, they don't even support building with VS, so |
|
@strega-nil This isn't 'our symlink support'; it's blowing up inside the port itself's build script. It will probably work if it gets run as admin. |
|
@BillyONeal this is true, but we don't support symlinks in bootstrapped vcpkg anyways. |
Describe the pull request
Add alternative download mirror for libressl port.
When ftp.openbsd.org is not available, use ftp.fau.de.
Sample build output